-
Notifications
You must be signed in to change notification settings - Fork 32
Check function run permissions 🎨 #7844
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Check function run permissions 🎨 #7844
Conversation
…parc-simcore into function_cache_check_success
…rc-simcore into handle_function_errors_api
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #7844 +/- ##
==========================================
- Coverage 86.74% 86.42% -0.32%
==========================================
Files 1852 1437 -415
Lines 71973 60230 -11743
Branches 1218 617 -601
==========================================
- Hits 62433 52056 -10377
+ Misses 9198 7975 -1223
+ Partials 342 199 -143
Continue to review full report in Codecov by Sentry.
🚀 New features to boost your workflow:
|
|
@mergify queue |
🟠 Waiting for conditions to match
|
matusdrobuliak66
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
General question → The lowest-level building blocks of our backend are projects wtih services inside, and they have their own sharing mechanism. Did you also consider situations where you share a function with someone, but they don't have access to the underlying projects or services?
matusdrobuliak66
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
I completely agree that we have to look into it further. This permissions were rather urgent to limit functions to single users, so not all use cases are covered yet (i.e. sharing functions). But tbh, I was kind of hoping the create study job etc would raise their own permission denied errors. But once we have a sharing endpoint, we should indeed throw errors in advance if a target user doesn't have access to the underlying project/services etc. |
services/api-server/src/simcore_service_api_server/api/routes/functions_routes.py
Show resolved
Hide resolved
|
|
@mergify refresh |
✅ Pull request refreshed |
360fa2e
into
ITISFoundation:master



What do these changes do?
Before running a function there is now a check to see if the user has execute permissions for the function.
Related issue/s
ITISFoundation/osparc-issues#1897
How to test
Execute a function you don't have execute access to
Dev-ops
No changes